Fractional applications product catalog

ABSTRACT

A method is provided for controlling access to applications available on a second network by a plurality of client mobile communications devices on a first network, wherein the first network includes (a) a first database comprising (i) a product catalog which contains a listing of a subset of the applications available on the second network, and (ii) a set of service rules which governs access to any of the applications in the product catalog by the client mobile communications devices, (b) a second database which specifies the applications that have been activated for each of the plurality of client mobile communications devices, and (c) a network appliance which is in communication with the second database and which grants access by each of the client mobile communications devices to the respective applications specified as active for that device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part application and claims thebenefit of U.S. Ser. No. 13/369,055 (Meyer et al.), filed on Feb. 8,2012, and entitled “SYSTEM AND METHOD FOR TASK SPECIFIC, METEREDBANDWIDTH CONTROL WITHIN SHARED CLIENT ENVIRONMENT ON MOBILECOMMUNICATIONS PLATFORMS”, which is incorporated herein by reference inits entirety, which claims the benefit of U.S. Provisional ApplicationSer. No. 61/440,471 (Meyer et al.), filed on Feb. 8, 2011, and entitled“SYSTEM AND METHOD FOR TASK SPECIFIC, METERED BANDWIDTH CONTROL WITHINSHARED CLIENT ENVIRONMENT ON MOBILE COMMUNICATIONS PLATFORMS”, which isalso incorporated herein by reference in its entirety, and which alsoclaims the benefit of U.S. Provisional Application Ser. No. 61/563,234(Meyer et al.), filed on Nov. 23, 2011, and entitled “SYSTEM AND METHODFOR TASK SPECIFIC, METERED BANDWIDTH CONTROL WITHIN SHARED CLIENTENVIRONMENT ON MOBILE COMMUNICATIONS PLATFORMS”, which is alsoincorporated herein by reference in its entirety.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to bandwidth allocation onmobile devices, and more particularly to systems and methods formetering bandwidth in a shared client environment on mobilecommunications devices.

BACKGROUND OF THE DISCLOSURE

Mobile network operators (MNOs) are responsible for an increasinglylarge portion of the communications network infrastructure in the modernworld. Typically, MNOs are defined as companies that have both alicensed frequency allocation of the radio spectrum over which they canoperate, and the required infrastructure needed to run an independentmobile network. Such infrastructure may include, for example, GSMs(global systems for mobile communications), CDMAs (code divisionmultiple access systems, which are digital radio systems that transmitstreams of bits or PN codes) and other core mobile network relatedinfrastructure, such as mobile switching centers (MSCs) and a radioaccess network.

As mobile networks have continued to develop, the companies providingthe services required to operate and use these networks have had toadopt newer business models to keep pace with evolving consumer demands.In combination with changing government regulations, this has led to theevolution of mobile virtual network operators (MVNOs).

Unlike MNOs, MVNOs do not have their own licensed frequency allocation,and frequently do not even have all of the infrastructure required toprovide mobile communications. Instead, MVNOs work in concert with othercompanies having these assets to provide mobile communications platformsto customers. In some instances, a company may operate as both an MNOand an MNVO. For example, if an MNO lacks a frequency spectrumallocation in a particular geographical region, it may operate as anMVNO in that region.

Significant efficiencies are obtained by the MVNO business model, sincean MVNO does not incur the significant capital expenditure on spectrumand infrastructure that an MNO does, nor does it have the time consumingtask of rolling out extensive radio infrastructure. Rather, thisdivision of responsibilities allows MVNOs to concentrate on their roleof value-added service providers, while many aspects of networkmaintenance and operation are performed by other companies behind thescenes.

The continued evolution of mobile communications networks has broughtabout even further specialization of services. Hence, while some MVNOsrun their own billing and customer care solutions (commonly known in theart as business support systems (BSS)), others delegate these servicesto a mobile virtual network enabler (MVNE). MVNEs provide services toMVNOs such as billing, network element provisioning, administration,operations, support of base station subsystems and operations supportsystems, and provision of back end network elements, to enable provisionof mobile network services such as cellular phone connectivity.

A MVNE typically does not have a relationship with end-user customers.Instead, an MVNE provides infrastructure and services to enable MVNOs tooffer services and have a relationship with end-user customers. Hence,MVNEs allow MVNOs to focus on their core strengths (typically brand,customer loyalty and marketing), while leaving the back-end enablementand operations to the MVNEs. An MVNE typically also has sharedrisk-reward arrangements with the MVNO with various kinds of revenuesharing models which are usually tied to the number of subscribers thatthe MVNO has projected in their business plan.

From a systems standpoint, designing an MVNE is a complex process thatfrequently includes taking commercial off-the-shelf applications andconverting them to work in a multi-tenancy model in a seamless fashion.Here, multi-tenancy refers to the principle in software architecturewhere a single instance of the software runs on a server, servingmultiple client organizations (tenants). Multi-tenancy may be contrastedwith a multi-instance architecture where separate software instances (orhardware systems) are set up for different client organizations.

With a multitenant architecture, a software application is designed tovirtually partition its data and configuration, and each clientorganization works with a customized virtual application instance. In amulti-tenancy environment, multiple customers share the sameapplication, running on the same operating system, on the same hardware,with the same data-storage mechanism. The distinction between thecustomers is achieved during application design, and hence, thecustomers do not share or see each other's data.

There are currently three main types of MVNEs. These may be categorizedaccording to their MVNO solutions:

(a) Aggregator MVNEs: these offer consulting and integration servicesand have bundled all of the back-office network components throughalliances. These promote their ability to quickly provide order-to-cashsolutions to MVNOs.

(b) Aggregator MVNEs with their own service delivery platforms (SDPs):this includes aggregators which have developed one or more back-officesolutions internally, and have complemented them with partnerships toprovide end-to-end enablement services.

(c) Specialized enablers: these offer only parts of the back-officenetwork such as messaging platforms, data platforms and billingsolutions. They are not solely focused on the MVNO market.

The SDP associated with an MVNE is a set of components that provides aservice delivery architecture (such as service creation, session control& protocols) for a particular type of service. SDPs became popular withthe introduction of open standards as IP technologies were introduced,and with the rapid expansion of Voice-over-IP (VoIP) for transmission ofvoice data over packet networks and the Session Initiation Protocol(SIP) for standardized media control, especially regarding enterprisevoice communication. In this new standards-supported environment,convergence of the voice and data worlds has become an avenue for theproduction of new and better consumer and business services.

The last few years have seen the introduction and proliferation ofvarious SIP programming libraries and products based on the relativelynew SIP standard, and the IP Multimedia Subsystem standard defined bythe 3GPP (a collaboration between groups of telecommunicationsassociations to make a globally applicable third-generation (3G) mobilephone system specification) has gained a substantial following. SDPs,whose power comes in large part from the quality and acceptance of thesesupporting standards, are rapidly gaining acceptance as widelyapplicable architectural patterns. SDPs are commonly considered for thetelco type environments as core systems which interconnect thecustomer's access and network infrastructure with BSS and OSS systems(operational support systems), the computer systems used bytelecommunications service providers (the term OSS is most frequentlyused to describe “network systems” dealing with the telecom networkitself, supporting processes such as maintaining network inventory,provisioning services, configuring network components, and managingfaults). SDPs in this context are usually associated to a particularservice regime such as mobile telephones or for converged services.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an illustration of a system architecture which may be used toimplement the systems and methodologies described herein.

FIG. 2 is an illustration of the architecture of an MNVE platform whichmay be utilized in the systems and methodologies disclosed herein.

FIG. 3 is an illustration of a screenshot of an embodiment of the GUI ofan on-device client in accordance with the teachings herein, whichdepicts the gauge feature used to depict the amount of connection timeor data remaining that is still available to a user.

FIGS. 4-11 are screenshots of methods for using the GUI of an on-deviceclient in accordance with the teachings herein for the presentation ofoffers to the user.

FIG. 12 is an illustration of an APN network architecture in anembodiment of a system in accordance with the teachings herein.

FIG. 13 is an illustration of the network architecture in an embodimentof a system in accordance with the teachings herein.

FIG. 14 is a diagram illustrating the structure of an APN.

FIG. 15 is a diagram of an implementation of a white label process formobile communications services in accordance with the teachings herein.

FIG. 16 is an illustration of an embodiment of a system architecturewhich may be utilized to provide content and applications for mobileservices within the context of some of the restricted or meteredbandwidth control paradigms of the types disclosed herein.

FIG. 17 is an illustration of an embodiment of a system architecturewhich may be utilized for administration, activation and provisioning ofcontent and application services within the context of some of therestricted or metered bandwidth control paradigms of the types disclosedherein.

FIG. 18 is an illustration of an embodiment of a system for implementingfractional applications in accordance with the teachings herein.

SUMMARY OF THE DISCLOSURE

In one aspect, a communications system is provided which comprises (a) afirst platform associated with an MVNE; (b) a second platform which isintegrated with said first platform and which has a plurality of tenantsassociated therewith, wherein each tenant has a set of mobilecommunications devices associated with it, wherein each mobilecommunications device in the set has an instance of a client installedon it which maintains an open connection to a communications network,and wherein each client is equipped with a graphical user interface(GUI); and (c) a group of offers selected by a tenant which aredisplayed on the GUI of each member of the set of mobile communicationsdevices associated with the tenant.

In another aspect, a method for providing offers over a mobilecommunications platform is provided. The method comprises (a) providinga first platform associated with an MVNE; (b) providing a secondplatform which is integrated with said first platform and which has aplurality of tenants associated therewith, wherein each tenant has a setof mobile communications devices associated with it, wherein each mobilecommunications device in the set has an instance of a client installedon it which maintains an open connection to a communications network,and wherein each client is equipped with a graphical user interface(GUI); and (c) displaying a plurality of icons on the GUI, wherein eachof said plurality of icons is associated with a third party serviceprovider and is hot-linked to a web page associated with the third partyservice provider.

In a further aspect, a data only device is provided which is equippedwith an always-hot connection to the Internet or to anothercommunications network.

In still another aspect, a method is provided for indicating theconsumption of network connectivity. The method comprises (a) providinga mobile communications device which is equipped with a GUI and which isconnected to a network; and (b) displaying a gauge on the GUI whichgraphically depicts the amount of network connectivity remaining.

In another aspect, a network adapter is provided which comprises (a) aconnector adapted to releasably engage a port in a mobile communicationsdevice, thereby bringing the network adapter into electricalcommunication with the mobile communications device; (b) a tangiblememory medium; and (c) a computer program disposed in or stored in saidtangible memory medium and containing suitable programming instructionswhich, when executed, provide the mobile communications device with freebroadband access to a network; wherein said free access is limited tospecific sites on the network.

In another aspect, a system is disclosed for providing broadbandcommunication services, comprising (a) a first entity which distributeswireless mobile communications devices to consumers; and (b) a secondentity which provides broadband wireless access to a network; whereinsaid second entity provides said broadband wireless access on a whitelabel basis to said first entity, and wherein said wireless mobilecommunications devices are configured to provide broadband wirelessaccess to the network under a private label applied by the first entityto the white label broadband wireless access.

In still another aspect, a method is disclosed for providing broadbandcommunication services. The method comprises (a) providing broadbandwireless access to a network; and (b) selling broadband wireless accessto a first entity on a white label basis, wherein said first entitydistributes wireless mobile communications devices to consumers, whereinsaid wireless mobile communications devices are configured to providebroadband wireless access to the network under a private label appliedby the first entity to the white label broadband wireless access.

In a further aspect, a method is disclosed for providing broadbandcommunication services. The method comprises (a) obtaining, on a whitelabel basis, broadband wireless access to a network; (b) applying aprivate label to the broadband wireless access; and (c) distributingwireless mobile communications devices to consumers, wherein saidwireless mobile communications devices are configured to providebroadband wireless access to the network under the private label.

In yet another aspect, a method is provided for controlling access toapplications or services over a network which includes (a) a pluralityof client mobile communications devices, and (b) a network applianceequipped with (i) a product catalog which contains a listing of aplurality of applications or services, and (ii) a set of service ruleswhich governs access to any of the applications or services in theproduct catalog by the client devices. The method comprises (A)receiving a request, from one of the plurality of client devices, for anaction selected from the group consisting of (a) activating anapplication or service, and (b) renewing a previously activatedapplication or service; (B) determining whether the request is allowableby (i) ascertaining whether the requested application or service is inthe product catalog, and (ii) ascertaining whether the service rulespermit the client device to access the requested application or service;(C) if the request is allowable, updating the network service applianceto indicate that the requested service or product is allowed for therequesting client device; and (D) if the request is not allowable,sending a notice to the requesting client device that access to therequested application or service has been denied.

In still another aspect, a method is provided for controlling access toapplications or services available on a second network by a plurality ofclient mobile communications devices on a first network, wherein thefirst network includes (a) a first database comprising (i) a productcatalog which contains a listing of a subset of the applications orservices available on the second network, and (ii) a set of servicerules which governs access to any of the applications or services in theproduct catalog by the client mobile communications devices; (b) asecond database which specifies the applications or services that havebeen activated for each of the plurality of client mobile communicationsdevices; and (c) a network appliance which is in communication with thesecond database and which grants access by each of the client mobilecommunications devices to the respective applications and servicesspecified as active for that device. The method includes (a) receiving arequest, from one of the plurality of client mobile communicationsdevices, for an action selected from the group consisting of (i)activating an application or service, and (ii) reactivating a previouslyactivated application or service; (b) determining whether the request isallowable by (i) ascertaining whether the requested application orservice is in the product catalog, and (ii) ascertaining whether theservice rules permit the client device to access the requestedapplication or service; (c) if the request is allowable, updating thesecond database to indicate that the application or service has beenactivated for the requesting client device; and (d) if the request isnot allowable, sending a notice to the requesting client device that therequest has been denied.

DETAILED DESCRIPTION A1. Overview

Despite the aforementioned advances in the art and the evolution ofSDPs, mobile communications platforms today are still limited in somematerial respects. In particular, such platforms, and the serviceofferings that have arisen around them, are premised on conventionalmodels for providing mobile broadband services, typically involvingmonthly or annual subscription fees. Such models do not account for orleverage the fact that many consumers access the Internet or othernetworks for specific purposes. Moreover, such models are primarilygeared towards providing services such as broadband access to consumers,without considering ways in which broadband access may be leveraged toprovide new methods and systems for consuming online services.

It has now been found that new service models and product offerings, andnew means for service consumption, may be provided by divorcing serviceofferings from conventional models of mobile broadband serviceconsumption. This end may be achieved, for example, through theprovision of a means by which consumers can consume servicesindependently of mobile broadband, and through a means by whichbusinesses are provided with new opportunities for deriving revenuestreams independently of mobile broadband. In particular, businessmodels are disclosed herein in which mobile broadband service may beused merely as a pipe for other services, offers and consumption models.

For example, in some of the systems and methodologies described herein,an on-device client is provided which is in communication with aplatform associated with an MNVO (this platform may be integrated withanother platform associated with an MVNE). The device may be in an“always connected” or “always hot” relationship with a mobile broadbandservice which is free to the user. However, unless the user buys generalbroadband access (by, for example, purchasing 30-day service pass), theuser can only go to a website associated with the MNVO (or to a set ofwebsites associated with or sponsored by tenants of the MNVO), and canonly get access to offers provided by tenants of the MNVO. Hence, theuser is given an “always hot” connection for free, but the user isrestricted in terms of what the user can do with the service.

This arrangement facilitates new ways of doing business and providingservices independently of mobile broadband service. This arrangementalso shifts the traditional paradigm away from purchasing network (e.g.,Internet) connectivity based on time and data, to one where connectivitymay be purchased based on what the consumer wants to do with theconnectivity.

As an example, a consumer electronics company that provides mobilecommunications devices to consumers may use such an arrangement tomaintain a hot connection to the device. This hot connection may then beutilized to stream or display offers to consumers and to provideconsumers with the ability to browse certain designated websites, evenwhen the consumer does not otherwise have access to the Internet oranother network. As a result, the company has the ability to engage inrevenue sharing activities with other parties in exchange for makingoffers from those parties available to the consumer over the “alwayshot” connection the company is providing.

As a further example, a service provider may use the systems andmethodologies described herein to provide session-based network accessto consumers. Hence, rather than paying for Internet access in general,the consumer has the ability to pay for a specific task, such as theability to access the Facebook™ social network ten times, or the abilityto watch a particular movie. The service provider (which may be, forexample, an MNVO or a tenant thereof) thus has the ability to engage inrevenue sharing with parties providing these sites or services, inexchange for making their site accessible or for providing a hotlink totheir site in the real estate provided on the consumer's mobilecommunications device.

B1. System Architecture

FIG. 1 illustrates a first particular, non-limiting embodiment of ageneral system architecture which may be used to implement some of thesystems and methodologies described herein. As seen therein, the systemarchitecture 101 comprises a first MVNE platform 103 which is associatedwith an MVNE, and a second MNVO platform 105 associated with an MNVO.

The MNVE platform 103 is preferably an SDP and hence contains a set ofcomponents that provides a service delivery architecture (such asservice creation, session control & protocols) for a particular type ofservice. The MNVE platform 103 has associated with it a first database133 containing operator information, SIM information and rate plans, anda second database 135 containing account information and hierarchies. Ofcourse, it will be appreciated that the MNVE platform 103 may containadditional databases, that the first 133 and second 135 databases may becombined into a single database, or that any the components of the first133 and second 135 databases may be disposed in other (possiblyadditional) databases.

The MNVO platform 105 is a multitenant platform which interfaces withthe MNVE platform 103 and with a plurality of tenant-branded on-deviceclients 107. The MNVO platform 105 has associated with it a firstdatabase 141 containing data for self-service first level support, and asecond 143 database containing marketing teasers and other advertisementdata. Of course, it will be appreciated that the MNVO platform 105 maycontain additional databases, that the first 141 and second 143databases may be combined into a single database, or that any thecomponents of the first 141 and second 143 databases may be disposed inother (possibly additional) databases.

The MNVO platform 105 is further equipped with suitable client proxiesto allow it to interface with the clients 107, and is also equipped withthe necessary software and hardware to implement the desiredfunctionalities 117 of the MNVO. Such functionalities 117 may include,but are not limited to, account registration, the ability to add moneyor credits to an account, starting a time pass, generatingnotifications, viewing or modifying account information, viewing SIMusage and account balances associated with a SIM, adding or transferringbalances between SIMs, providing marketing teasers, and supporting aself-help tutorial, which may include frequently asked questions (FAQs)or information about how to perform common tasks (“how-to's”).

The MNVO platform 105 and the MNVE platform 105 exchange information andotherwise cooperate to support various functionalities 119, 120 for theclients 107 and the associated users. Such functionalities 120 mayinclude, but are not limited to, account registration, the ability toadd money or credits to an account, starting a time pass, generatingnotifications, viewing or modifying account information, viewing SIMusage and account balances associated with a SIM, and adding ortransferring balances between SIMs. These functionalities 119 mayfurther include services required to support the operations of the MNVO,which may include, but are not limited to, providing reports,maintaining a network operations center (NOC), processing operatorsettlements, and providing support services to the MNVO. Such supportservices may include, but are not limited to, SIM logistics (such asrequesting shipment of SIMs), activating, deactivating or blocking SIMs,processing trouble tickets, and modifying balances (e.g., applyingcredits or debits).

The reporting functionalities provided by the MNVO platform 105 includeservice reporting 111 and royalty reporting 113 to the tenants. Theroyalty reports typically include details on network usage and revenuesharing on a tenant-by-tenant basis. The service reports typicallyinclude details regarding the number of consumers that activated serviceon a given day, the number of users that have received their machinesand powered up, and the number of users that have not used the servicerecently.

As previously noted, the MNVO platform 105 interfaces with a pluralityof tenant-branded on-device clients 107. The clients 107 may be thick orthin clients, and may be browser-based. Each client 107 is equipped withan application programming interface (API) which has been defined to it.An MNVO may use the MNVO platform 105 to provide a tenant withwhite-label services so that the tenant has the ability to use theclient 107 provided by the MNVO, and can simply brand it. The tenant mayalso provide its own client 107 and may cut to the API. As part of theservice offering, the MNVO platform 105 provides Wi-Fi, fixed and mobilebroadband connectivity to its tenants.

Preferably, the MNVO works with each of the tenants to define a set ofservices the tenant wants to go to market with, establish goals andrequirements, assemble the business processes required by the tenant,and instrument the client (in both the MVNE 103 and MVNO 105 platforms).From a consumer perspective, then, the consumer buys a service which issold by the MNVO, and the MNVO and tenant work together to support thecare of that service.

The MNVO platform 105 is preferably implemented on a server which is incommunication with a self-service portal 109. The self-service portal109 is defined in both the browser and the on-device clients 107, and ispreferably implemented with a multi-layer protocol. The self-serviceportal 109 provides self-service 1^(st) level support to consumers, andallows them to access the functionalities 117 described above. The MNVOplatform 105 is also preferably equipped with teaser interfaces 115(such as e-mail) which may be used for marketing and advertisementpurposes.

B2. MNVE Platform

The MNVE platform 103 is a service delivery platform through which theMNVE interfaces with an MNO 127 and a service aggregator 125. The MNVEplatform 103 interacts with modules or services which provide e-mailreceipt 131, a payment gateway 123 and a service for order fulfillmentand returns 121. The latter service processes theactivation/deactivation of IMSIs (international mobile subscriberidentities), subscriber names and addresses, free day passes, andservice IDs.

Referring still to FIG. 1, the MNVE platform 103 acts as a servicedelivery platform which preferably provides comprehensive convergentrating and charging capabilities to handle advanced prepaid, postpaid,interconnect and roaming requirements. This platform may leverage asoftware solution which offers a complete solution for multiple playcustomer care and billing (CC&B). The CC&B may be modular and rapidlydeployable, and preferably supports such processes as customerinitiation, order management, customer activation, service provisioning,customer care, usage rating, invoicing, accounts receivable, collectionsand reporting. The software solution also preferably allows the MVNO tomanage complex, multi-layered relationships and create service packagesconsisting of multiple voice and value added services (VAS). Thesoftware solution may be deployed in a multi-tenant configuration so asto enable the SDP to support specific customer management processes, andto order management workflows and billing configurations for each of itsMNVO customers on a single instance of the software.

The software solution preferably affords the flexibility for the MNVO toprovide custom solutions which are configured to the specificoperational requirements of the MNVO. The MNVO customers benefit fromthe ability to support their brands with multiple service combinationsand advanced rating and charging options.

The software suite may also provide a range of customer management andbilling solutions which enable the MNVO to deliver a personalized andeffective customer experience, expand service and product offerings andincrease operational efficiency. The software solution may be based on amodular product portfolio that includes billing, rating, productcatalog, CRM, self care, e-billing and data analysis. In a preferredembodiment, the software solution includes the following modules:

(a) a web-based customer management module that centrally managescustomer information and processes the workflow of customer lifecycleevents;

(b) an event and usage based rating engine which processes complexrating schemes in real-time and supports rating hierarchies for vendor,partner and other third party compensation;

© a robust billing and invoicing engine that processes invoices,calculates periodic charges (usage, recurring, one-time, credits) andapplies applicable discounts, promotions and taxes; and

(d) catalog software that enables the MNVO to define and manage anenterprise catalog of convergent product offerings and packages withadvanced pricing and discount schemes.

B2. MNVE Platform Components Customer Management Module

The web-based customer management module enables the MNVO to establishan operational framework to build a customer base, while also attractingnew customers. This module is preferably a web-based customer managementapplication which provides service providers with the followingfunctionalities: (a) customer relationship management (CRM), (b) partnermanagement, (c) order management, (d) workforce management, (e) resourcemanagement, (f) service configuration and provisioning, (g) accountsreceivable, and (h) cash collections. These functionalities arepreferably integrated into a single, unified front-end HTML frameworkthat provides a detailed view of all customer information, whilestreamlining the business processes between activities.

The web-based customer management module may be adapted to provide a360° view of all customer related information and activities. Thecustomer centric functionality of the customer management module enablescustomer service representatives (CSRs) to quickly respond to allcustomer inquiries and requests from a centralized application. Hence,with the customer management module, CSRs can avoid having to accessmultiple applications or having to transfer customers to otherdepartments.

The customer management module also preferably processes customerlifecycle events using a flexible, rule-based workflow mechanism andsupports advanced task management with resolutions and escalationprocedures. Customer-oriented functions, such as customer registration,service activation, online pricing plan assignment, customer request andcomplaint handling, the issuance of letters and notices, and customerprofile modification, may all be supported within the framework of anautomated workflow mechanism.

The order management processes for the fulfillment of multiple playservice orders in the customer management module are processed by anembedded workflow engine. Each step of the order management activitiesare configured according to specific operational business processes andpolicies covering the initiation, modification and termination ofservices, the automatic provisioning of interfaces, and the fulfillmentof orders to external devices and third parties. The order managementfeatures of the customer management module support the configuration,validation and assignment of complex services and bundles.

B3. MNVE Platform Components Rating Engine

The event and usage based rating engine processes multiple play servicesand matrix structured rating schemes. This engine allows serviceproviders to capture all revenue generating opportunities by processingcomplicated usage and event billing scenarios and hierarchical structurerating plans.

The event and usage based rating engine is preferably a carrier-graderating engine that supports high volume processing of real-time andbatch event and usage records. The event and usage based rating enginehandles traditional retail, business and inter-carrier rating scenarios,as well as multilayered rating hierarchies to support partner and vendorrelationships. The event and usage based rating engine is preferablycapable of rating expanded services, incentive-based pricing, discountstructures and loyalty schemes. The event and usage based rating enginegathers usage information from internal and external sources, validatesand formats the information, identifies the subscribers to be billed andrates the usage according specific subscriber usage plans. The event andusage based rating engine also preferably contains features formonitoring and controlling processes, including exception handling,re-rating and rollback functionalities.

From a single instance of the event and usage based rating engine, anycombination of products and services may be rated. As a service-neutralrating engine, the event and usage based rating engine can process ahigh volume of usage records acquired from various external devices andgateways, while handling multiple input streams simultaneously. Theevent and usage based rating engine may also support pay-per-speed,pay-per-bandwidth, pay-per-view, pay-per-event, volume-based and IPtime-based events.

The event and usage based rating engine preferably incorporates servicelevel agreements and network quality of service ratings to accuratelycharge for usage. These rating capabilities may allow for processingboth in-collects and out-collects for intricate partner compensation andreconciliation. The event and usage based rating engine also reevaluatesdata records to check for fraud, while rated usage output can beexported to external decision support systems (DSS) and data warehousingapplications.

Standalone or multiple instances of the event and usage based ratingengine may be deployed and run in parallel to increase operationalthroughput. The event and usage based rating engine preferably has ascalable design that is capable of handling rapid and unlimitedincreases in customer numbers and traffic volume.

B4. MNVE Platform Components Billing and Invoicing Engine

The billing and invoicing engine compiles, generates and summarizes theelements that make up a customer invoice. The billing and invoicingengine calculates recurring charges based on customer price plans andcompiles other relevant charges for a billing period. The billing andinvoicing engine calculates the applicable taxes for the invoiceaccording to each customer's tax plan.

The billing and invoicing engine is preferably a convergent billingengine that is able to calculate charges for a multiple of products andservices on a consolidated bill or bill for each product and serviceseparately. The billing and invoicing engine helps expand revenuestreams by supporting volume discounts, cross-product discounts, rewardsand promotions.

With respect to volume discounts, the billing and invoicing engine ispreferably adapted to aggregate customer usage according to severalcategories and to apply appropriate volume discounts. With respect tocross-product discounts, the billing and invoicing engine is preferablyadapted to apply discounts based on diverse combinations of products andpackages. With respect to rewards, the billing and invoicing engine ispreferably adapted to dynamically calculate discount eligibility basedon customer profiles and usages volumes, and to apply rewards in theform of discounts on the invoice, free usage or bonus points. Withrespect to promotions, the billing and invoicing engine preferablyoperates to ensure that customer usage of promotional offers remainwithin predefined limitations.

The billing and invoicing engine preferably allows invoices to be splitinto multiple billing cycles, while numerous bill runs can be validatedand authorized in parallel. The billing and invoicing engine alsopreferably supports prorated billing for products and plans, accordingto actual active dates, and further preferably includes hot billfunctionality for out-of-cycle and on-the-fly billing.

The billing and invoicing engine helps to ensure billing accuracythrough an established bill verification and approval process, andprovides detailed log files showing generation statistics in order toreduce billing errors. The billing and invoicing engine also preferablyincludes a rollback functionality that allows bill generations to bereversed and new invoices to be created.

The billing and invoicing engine preferably supports multiple billingformats and multilingual invoices according to specific operational andregional needs. The billing and invoicing engine may also handle thirdparty billing to support the needs of distribution partners and revenuesharing scenarios. Preferably, the billing and invoicing engine outputsXML, PDF or PostScript files and includes a configurable archivingsystem.

The billing and invoicing engine is preferably built with anarchitecture that enables multiple bill runs to be processed inparallel. Preferably, bills can be viewed during the validation stagebefore being committed to the storage database in order to performquality assurance on output.

B5. MNVE Platform Components Catalog Software

The catalog software is preferably an enterprise product catalog thatallows service providers to construct and manage a catalog of complexproduct and package offerings with advanced price discount schemes. Thecatalog software may be utilized to improve operational efficiency byremoving the need to manage multiple instances of product information indifferent OSS/BSS systems.

The catalog software preferably integrates product information withpricing strategies and synchronizes the product catalog across allOSS/BSS systems. It may support customer-based processes with relevantproduct information related to customer product fit.

Order management processes are preferably centrally defined in thecatalog software so as to enable the configuration and validation ofproduct fulfillment. The product codes stored in the catalog softwaremay be mapped from one system to another for adjusting revenues andcomputing cost and revenue centers. Moreover, provisioning parametersrelating to different product lines may be configured in the catalogsoftware, thereby enabling centralized and unified control of thecapabilities of various network elements. Also, price catalog andbilling parameters may be managed centrally in the catalog software,thereby removing the need to define and maintain product informationseparately in different billing systems.

The catalog software may be adapted to support multiple play productsand packages from fixed line, ISP, mobile, cable TV and utilities-basedservices. The catalog software may be adapted to allow multiple internaldepartments within a service provider to easily control various aspectsof product offerings, configurations, pricing and discount schemes. Thecatalog software is preferably equipped with an automated workflowmechanism that enables separate product profiles and tasks to be definedand initiated by other applications in order to achieve a centralizedrepository for controlling product management.

The catalog software is preferably adapted to allow service providers todefine prices for various products and packages and to adjust tariffsand create discount plans. The catalog software also preferably allowsfor the bundling of products across different business lines into newpackages.

The catalog software may also serve as a centralized knowledge centerfor marketing and technical information about all products and packages.As a result, the catalog software streamlines business processes andreduces the time-to-market with associated defining new products andpackages, while reducing operational overhead.

C1. Functionalities of MNVE Platform

FIG. 2 illustrates the functionalities of a preferred embodiment of theMNVE platform 201. The MNVE platform 201 has a front end 205 and a backend 207 within the infrastructure of the MNVO 203, and a set of businesssupport systems 209. The front end 205 and a back end 207 may beaddressed through a client 231. Each of the functionalities provided bythe MNVE is described in greater detail TABLE 1 below:

TABLE 1 Functionalities of MNVE Platform MODULES DESCRIPTION SMSCHandles SMS and real-time charging of SMS. Prior to granting an SMS(211) submission (or reception) the SMS Charger requests permission fromCharging. Real-time charging is applicable to roaming- and home networkusers. MMSC Handles MMS traffic together with real-time charging of MMS.Prior to (213) granting an MMS submission (or reception) the MMS Chargerrequests permission from Charging. Real-time charging is applicable toroaming- and home network users. SCP Handles call control and real-timecharging of voice/data/fax/video calls. (215) All traffic is monitoredin real time with refusal of service if e.g. insufficient funds. GGSN(incl. Handles real-time charging of packet traffic. Prior to grantingdata Packet Charger) traffic the Packet Charger requests permission fromCharging. Real-time (217) charging is applicable to roaming- and homenetwork users. Event Charger Handles event charging requests fromexternal applications such as (219) content providers and value-addedservice platforms. Number Number portability gives the service providerthe means to use number Portability DB portability information (networkoperator ID) for rating and traffic (221) routing. Voice Mail Flexibleand integrated solution for recording and storage of voice (213)messages. Includes features such as multi-language support, autoprovisioning and self management (via USSD, etc), complete messageconvergence, e.g. MMS and e-mail voice message delivery. IVR Handlesvarious subscriber interactions, like top up management and (225)customer self care with interactive voice responses. USSD Handlesvarious subscriber interactions, like top up management and (227)customer self care with interactive text message. The USSD Gateway alsoacts as a USSD Menu Server, interacting with external applications. WAPGateway Handles all WAP traffic. (229) Charging Receives chargingrequests and ensures these are rated, reserved and committed. RatingResponsible for rating all traffic types for all subscription types.Subscriber Contains customer, account and subscription data. Greatflexibility in services creating customer structures/packages, loyaltybonuses, etc. Includes tools to administrate customer-related logistics(in batch or individually) for phone numbers and SIM cards. VouchersVoucher Management handles creation and management of vouchers, virtualcalling cards and PIN codes. Full voucher lifecycle logistics aresupported. B2B and B2C Responsible for handling billing, i.e. generationof invoicing files. accumulations Contains CDR data that is kept onlinefor a set period and then archived/exported to other systems. Outboundand Outbound provisioning is handled towards external systems such asinbound HLR. Inbound provisioning is handled via CAI (Customerprovisioning Administration Interface). Discounting Accumulation baseddiscounts. TAP Import Importing and B2C charging of TAP3 roaming files.Client The Client is a graphical user interface (GUI) for configurationand creation of products and services, rate plans and billing schemes,as well as administration and management of the system.

D1. On-Device Client

FIG. 3 depicts a particular, non-limiting embodiment of a GUI 401 whichmay be associated with an instance of a client installed on a mobilecommunications device in some of the systems and methodologies disclosedherein. In some such embodiments, each tenant on an MNVO (see, e.g.,FIG. 1) may have a set of mobile communications devices associated withit, and each mobile communications device in a set may have an instanceof such a client installed on it.

As seen in FIG. 3, the GUI 401 has a first display portion 403 on whicha plurality of tiles 405 or icons are displayed, and a second displayportion 407 on which status information 409 relating to the user'saccount is displayed.

The status information 409 includes a gauge 411, similar to a fuel gaugeon an automobile display. The gauge provides a real-time indication ofresource consumption and, in particular, an indication of how muchbandwidth usage or access or connectivity time is available to the userbefore replenishment will be necessary. Such a gauge 411 may beimplemented by, for example, integrating time and bandwidth consumptionrates into a numerical scale, in a manner analogous to the way a fuelconsumption gauge on an automobile integrates the amount of fuelremaining in the fuel tank with the fuel consumption rate. Hence, thegauge 411 provides a visual indication of the consumption of data,network time or connectivity occurring on a device (such as, forexample, a mobile communications device), and may be adjusted as any ofthese resources are consumed so that it depicts the current amount ofnetwork the resource remaining Consumption may be depicted as a functionof any suitable variable, or combination of variables including, but notlimited to, time and data transfer.

It will be appreciated that the gauge 411 may assume a variety ofdifferent formats. For example, into addition to the “fuel gauge” typeembodiment described above, the gauge 411 may take the form of, or mayinclude, various dials, graphs, bars, or partially shaded figures orgradients. By way of example, but not limitation, the gauge may utilizeor take the form of any of the graphical depictions commonly used toindicate the remaining amount of battery life, fuel, or other consumablecommodities in business or consumer oriented devices.

Each of the tiles 405 or icons in the first display portion 403 of theGUI 401 is an offer for a service. These offers may be provided by, orassociated with, one or more tenants on an MNVO platform of the typedepicted in FIG. 1. Such a tenant may be, for example, a third partyservice provider, and the tiles or icons 405 may be hot-linked to a webpage associated with the third party service provider. In someembodiments, each tenant may have a plurality of mobile communicationsdevices associated with it. In some embodiments, such devices may be“data only” devices.

Each offer can be expanded upon (in the second display portion 407) byselecting the tile 405 or by dragging the tile 405 into the seconddisplay portion 407, which causes a page to be displayed on the seconddisplay portion 407 of the GUI 401 that contains the details of theoffer. In other words, selecting a tile 405 causes the focus of thesecond display portion 407 to change to the context of the offer.

This process is illustrated in FIGS. 4-5 for a particular offer 416 (seeFIG. 5) having to do with access to the Facebook™ social network. Inparticular, the offer 416 provides the user with free access to theFacebook™ social network, while other parts of the Internet or othernetworks may be unavailable to the user or may require a subscription,charge, time pass, or the like. The connection to the communicationsnetwork that is provided to the user may be “always hot”. Hence, in thecontext of the foregoing example, in such embodiments, the user mayenjoy continuous access to the Facebook™ social network for as long asthe offer is in effect.

Referring again to FIGS. 4-5, selecting a tile 405 may also causerevision in the gauge 411 shown in FIG. 3 to the gauge 413 shown inFIGS. 4-5. In particular, in the embodiment depicted, the gauge 411 ofFIG. 3 is revised into the dual gauge 413 of FIG. 4 which shows thebandwidth and time remaining Selecting a tile may also activate one ormore icons or indicia 415, such as the depicted “Macheen Inside”indicia, which may be displayed in a placeholder in the second displayportion 407.

As shown in FIG. 5, the offer displayed in the second display portion407 may include a radio button 417 or other means by which the user mayindicate acceptance of the offer. When the user thus indicatesacceptance of the offer, the icon corresponding to that service is addedto the next free tile position available in the active services fieldwithin the first display portion 403 of the GUI 401. As shown in FIG. 6,this causes the second display portion 407 of the GUI 401 to display aconfiguration window 418 which allows the user to configure certainparameters of the service, and also causes display of a call-out 420that indicates that the experience involves free bandwidth.

When the “save” radio button 422 is selected, the panel refreshes toshow the current state of the service as shown in FIG. 7 which, in theembodiment depicted, contains information about the user's Facebook™account 424. The resulting page is refreshed anytime the user selectsthe “Refresh now” radio button 419 or the corresponding panel focus icon405. Clicking on any part of the notification panel 426 or selecting the“Go Online to Facebook Now” radio button 421 will take the user to theuser's Facebook™ homepage, and will prompt the user to start a new timepass if there is currently no active session.

FIGS. 8-9 show another offer 428 (expanded), which may be accepted byselecting the “Accept” radio button 429 in the second display portion407. This particular offer 428 is for free access to Yahoo!™ Local, aweb portal for businesses, organizations, and other items of localinterest 431 (see FIG. 9). Preferably, a heavier style is utilized andis associated with services that are available to dock, rather than justbeing used on the fly. By contrast, FIG. 10 shows a different offer 430(expanded) which is associated with services used on the fly, such asthe indicated product registration.

FIG. 11 shows another expanded offer 432, this one offering a selectionof movies from Amazon's Instant Video™ service. This offer 432illustrates the difference between one time transactions involving anaccount charge (here, $10 per movie purchased), versus a dockedtransaction involving a settlement.

Various modifications are possible with embodiments of the type depictedin FIGS. 3-11. For example, the order in which the tiles 405 or iconsare displayed on the first display portion 403 of the GUI 401 may bedictated by various considerations, such as the order in which each tile405 or icon was selected, or the frequency with which each tile 405 oricon was selected. Moreover, while it is preferred that the tiles 405 oricons all have the same size, embodiments are also possible in whichthis is not the case. Embodiments are also possible wherein a maximumsize is dictated for the tiles 405 or icons, or wherein each icon isdisplayed within a tile 405 of fixed dimensions.

The manner in which the client is resident on the mobile communicationsdevice, or on a memory or storage medium associated with the mobilecommunications device, may also vary. For example, in some embodiments,the client may comprise software which is downloaded on a mobilecommunications device or is installed on the device by the devicemanufacturer, by a tenant on an MNVO, or by a party to a white labelprocess or arrangement.

In other embodiments, the client (or a computer program or a set ofsuitable programming instructions which, when executed, provide themobile communications device with free access to a network, subject to apredefined set of restrictions) may be resident on a network accessdevice, such as a network access card or a wireless adapter. Inparticular, the client may be resident on or stored in a tangible mediumor memory associated with such a device. Such a network access devicemay be equipped with a USB adapter or another suitable connector whichis adapted to releasably engage a port (which may be, for example, a USBport) in, or is otherwise adapted to couple with, a mobilecommunications device, thereby bringing the network access device intoelectrical (or possibly optical) communication with the mobilecommunications device.

Embodiments of the type depicted in FIGS. 3-11 may also enable a widevariety of restricted access and consumption models. For example, insome embodiments, free access (or free broadband access) to a networkmay be limited to a single site on the network, or to a set of sites onthe network (these sites may be, for example, sites associated with ordesignated by tenants on an MNVO). Access to other sites on the networkmay be extended on a subscription or pay-per-use basis, on a timelimited basis (e.g., 30 minutes of access to the Wall Street Journalsite per day), on a bandwidth usage, limitation, or allocation basis, orsubject to various other restrictions or requirements. For example, suchaccess may be subject to the requirement that a user view anadvertisement prior to gaining access to a site or set of sites on thenetwork.

C1. Metered Bandwidth Control

One significant feature of some of the systems and methodologiesdisclosed herein is the ability they provide to use Access Point Names(APNs) to create new business models to settle out mobile broadbandaccess and/or usage. APNs are configurable network identifiers which areused by mobile communications devices when connecting to a GSM carrier(GSM refers to the Global System for Mobile Communications, a popularstandard for mobile telephony system). The carrier uses the APN todetermine the type of network connection that should be created,including such details as the IP address (or addresses) that should beassigned to the mobile communications device, the security methods thatshould be employed, and how the device should be connected to a privatecustomer network. The APN identifies an IP packet data network (PDN)that a mobile data user wants to communicate with, and may also beutilized to define the type of service provided by the PDN (e.g.,connection to a wireless application protocol (WAP) server, multimediamessaging service (MMS), and the like).

As shown in FIG. 14, an APN 501 consists of a network identifier 503 andan operator identifier 505. The network identifier 503 defines theexternal network to which the gateway GPRS support node (GGSN) isconnected, and may also include the service requested by the user. Theoperator identifier 505 defines the specific operator's packet domainnetwork in which the GGSN is located.

The GGSN is a main component of the GPRS network, and is responsible forthe interworking between the GPRS network and external packet switchednetworks, such as the Internet and X.25 WiMax networks. The GGSN acts asa router to a sub-network by hiding the GPRS infrastructure from theexternal network. When the GGSN receives data addressed to a specificuser, it checks if the user is active. If it is, the GGSN forwards thedata to the Serving GPRS Support Node (SGSN) serving the mobile user,but if the mobile user is inactive, the data is discarded. On the otherhand, mobile-originated packets are routed to the correct network by theGGSN.

The SGSN is responsible for the delivery of data packets to and frommobile stations within its geographical service area. The SGSNimplements packet routing and transfer, mobility management(attach/detach and location management), logical link management, andauthentication and charging functions. The location register of the SGSNstores location information, such as, for example, current cell andcurrent visitor location register (VLR). The visitor location registeris a temporary database of the subscribers who have roamed into thejurisdiction of the MSC (Mobile Switching Center) which it serves. Thelocation register of the SGSN also stores the user profiles (such as,for example, IMSI and addresses used in the packet data network) of allGPRS users registered with the SGSN. The IMSI (international mobilesubscriber identity) is a unique identification associated with all GSMand UMTS (Universal Mobile Telecommunications System) network mobilephone users, which is typically stored as a 64-bit field in the SIMinside the phone.

APNs are utilized in an APN resolution process. APN resolution is theprocess of domain name system (DNS) look-up to determine the IP addressof the GGSN that provides connectivity to the PDN identified by the APN.When a GPRS mobile phone sets up a data connection which it wants toconnect to, APN resolution is used to select the GGSN and provide an IPaddress.

In some embodiments of the systems and methodologies described herein, aservice provider may create and use one or more unique APNs to controlaccess and/or charging for mobile broadband usage. A client associatedwith the service provider may control access to the service provider'smarketing bandwidth APN. Consequently, traffic may be allowed or deniedbased on the application the customer is using.

Such an approach has several possible advantages. For example, it may nolonger necessary when using this approach for the subscriber to purchasea general mobile Internet access session. In addition, a clientassociated with the service provider may allow access based on rulesestablished by the service provider and/or the tenants associated withthe service provider. As an example, these rules may (a) allow freeaccess to client administration services provided by the serviceprovider; (b) allow the subscriber to browse, buy or use content on thesubscriber's device; (c) allow the subscriber to access or use teasers;and (d) allow the subscriber to access specific applications.

The foregoing configuration is illustrated in the system 601 depicted inFIG. 12. As seen therein, a client 603 associated with the serviceprovider or MNVO (Macheen) is configured to use APN IP addresses 605 forpaid service and marketing zones. The APN is configured to the MNOoperator 607, which itself is configured or managed by the architectureof the service provider platform 609. This platform architecture checksaccess rights to the Internet 611 or other network, begins the meteringprocess, and proxies to the IP address requested. If there is a clientservice panel request, the service provider makes API calls to the MNVEand returns information through the service provider and to the client603. A regular APN is used in the event that the subscriber has a paidplan. If the request is to the Marketing Zone, then the APN is usedwhich is associated with that pricing, charging or settlement model.Suitable communications links 621, 623, 625, 627, 629 and 631 may beemployed in the architecture of the service provider platform 609 toenable the foregoing functionalities.

C2. Metered Bandwidth Control

Some of the systems and methodologies disclosed herein are advantageousin that they provide the ability to implement white label processes forservices to mobile communications devices. FIG. 13 depicts furtherdetails of a particular, non-limiting embodiment of a system 701 overwhich such a white label process may be implemented, it being understoodthat this system is preferably being implemented within the generalsystem architecture depicted in FIG. 1.

The system 701 depicted in FIG. 13 includes a service platform 703 andone or more tenants 705. The service platform 703 includes both aservice provider portion 702 and a subscriber portion 704. The serviceprovider portion 702 includes such elements as the MNO 713, the MNVE717, the leased line 716 between the MNO 713 and the MNVE 717, a controlmodule 719, a help desk 721 for processing service tickets, and apayment gateway 723. The subscriber portion includes such elements asemail service 707, the device client 709 and a self service portal 711.Associated with the service platform 703 are such support services astenant support 725, system support 727, financial operations 729, andsystem service operations 731. System service operations 731 work with alogistics provider 733 for the order and shipment of SIMS cards.

Various reporting and point of sale (POS) services are provided to thetenant 705. These include service reports (S/M) 741, settlement reports(finance) 743 and hosted offer management (Ops) 745.

Typically, the business model of an MNVO revolves around selling mobileservices to businesses and consumers. However, the white label processesdescribed herein has a business model which is typically business tobusiness to business, or business to business to consumer.

In the particular embodiment depicted, the process allows a first entity(such as, for example, an MVNO or MNO) to provide a second entity with amobile service that they can brand as their own and market or sell aspart of their bill of materials for the devices. For example, the secondentity may be a consumer electronics company or other distributor ormanufacturer of consumer devices (and especially mobile technologyplatforms, such as mobile communications devices and mobile computingdevices). This arrangement allows such second entities to create uniquemobile offerings that showcase their devices and enhance their brandidentity, without requiring the infrastructure and overhead typicallyassociated with developing and operating a mobile network.

FIG. 15 illustrates a particular, non-limiting embodiment of a set ofservice interfaces 801 that may be associated with the aforementionedwhite label processes for services to mobile communications devices. Asseen therein, the interface 801 comprises a set of service providerprocesses 803 and a set of tenant integration points 805. The set ofservice provider processes 803 include such processes as integration ofthe order fulfillment process, white labeling to mobile clients, theprovision of standard reports, the provision and review of content fortenant POS and sales training, the development, training andimplementation of the tenant's 1^(st) level support team on service, andthe development and review of service definition with the tenant productgroup.

These processes are provided through service interfaces to varioustenant integration points, such as order fulfillment 811, clientapplications 813, service reporting 815, point of sale (POS) 817, 1^(st)level support 819 and service definition 821. The set of serviceinterfaces 801 depicted in FIG. 16 facilitates or enables a variety ofnovel services. For example, it allows access to a specific site orsites on the Internet or on another network, while blocking access toall other sites on the network when the host device is connected tomobile broadband. This service may be provided to the entire customerbase, to a subset of the customer base identified by an attributedefined by the tenant, or to a single customer.

The service may be provisioned in a variety of ways. For example, theservice may be provisioned in advance with start times and ends times,or it may be provisioned in real time (instantly) based on selectionsmade by the user from among various options presented. The service mayalso be defined such that access to the service lasts indefinitely, endsat a time specified by the service provider, or ends after a definednumber of minutes or a defined amount of data. Access to the service mayalso end in response to a new user action, such as clicking a differenttile for access to a different website (see the embodiment of FIGS.3-11). The service may be provisioned in real time (instantly) inresponse to user actions such as watching an advertisement, filling outa survey, clicking a link, or referring other users. Access to contentmay also be provided as a fixed charge, or free of charge to thesubscriber by time increment.

Content services may be targeted to small or medium businesses, toenterprises, and/or to consumers. The content service definition mayinclude access to one network or Internet service (e.g., a single URL),or a group of network or Internet services (e.g., many URLs). Thecontent service may also be defined as access to the Internet or othernetwork for a specific device application (such as, for example, games,email, or IM).

In some embodiments, the methodologies described herein may beimplemented through the provision of a suitable hardware device thatprovides a mobile broadband connection. Such hardware may take the form,for example, of a USB stick, an internal modem, a network adapter, oranother suitable device that allows access to pre-defined websites whena connection is made, but blocks access to all other websites unless theuser purchases access to the full Internet. The hardware device mayprovide session-based access to the Internet or other networks based ontime or data limits.

In some embodiments, the network or Internet access provided to a usermay allow a specific application or set of applications on the user'sdevice (or on the host device) to access the network, while denyingaccess to other applications on the host device. For example, in aparticular embodiment, Yahoo Instant Messenger™ may be permitted toaccess the Internet or other network on the host device, while otherprograms such as Skype™ and Internet Explorer™ are denied access. Inthese embodiments, service may be provided in all the same ways asindicated above.

In some embodiments, network traffic may be allowed from a specificprotocol or protocols, while network traffic from other protocols isdenied. For example, HTTP/HTTPS traffic may be allowed, but video may bedenied (at least on a free-of-charge basis) using RTSP (Real TimeStreaming Protocol) and/or HTTP/HTTPS as the blocker. This approach mayallow the service provider and its tenants more control over the contentthat is accessed and consumed by users. By way of example, access toFacebook™ may be offered, but the user may not be permitted to watchvideos. Service may be provided in all the same ways as indicated above.

In some embodiments, the systems and methodologies described herein mayprovide a customized display experience (different landing page). Thelanding page display may be based, for example, on (a) region, (b)machine or device type, (c) tenant, or (d) corporate sponsor. By way ofillustration, each tenant on an MNVO may have one or more corporatesponsors associated with it, and the landing page experienced by aparticular user or employed by an instance of a client may be dictatedby the corporate sponsor of the tenant associated with that user orclient. This approach allows for a customized icon/tile selection basedon one or more of the foregoing factors.

One skilled in the art will appreciate that the services describedherein are not mutually exclusive. Rather, they may be accumulated ontop of each other. For example, a customer may purchase or receive freeaccess to one Internet service (URL) for a given timeframe (for example,one limited to a predetermined start time and end time) by taking acertain action, and may then receive free access (or purchase access) toanother Internet service (URL) on top of the existing access (that is,the user may accumulate Internet services access or multiple URLs). Insome embodiments, free access may also terminate in response to anaction taken by a user (such as, for example, clicking on a hot-link foraccess to a particular website, set of web sites, or class of websites). The customer may also receive promotions for all SMB to receiveaccess to the tenant's support portal, and may then purchase access tospecific Internet services (URLs) (in other words, the customer mayaccumulate free access based on account characteristics, and individualaccess based on purchases). Of course, it will be appreciated that anycombination of the previously outlined services may be accumulated oneon top of another.

FIG. 16 depicts a particular, non-limiting embodiment of a systemarchitecture 901 which may be utilized to provide content andapplications for mobile services within the context of some of therestricted or metered bandwidth control paradigms of the types disclosedherein. As seen therein, when a mobile device/subscriber 904 requestsaccess 903 to the Internet 902 over a modem, a determination is made 905by the mobile virtual network operator 906 as to whether there is anactive session 907 (based on time and data) that allows the mobiledevice/subscriber 904 to access the entire Internet 902. If thedetermination is made 909 that there is no active session (based on timeand data), then the mobile device/subscriber 904 is validated oridentified 911 and content services are provisioned 913. The contentrules 914 for the provisioned services are then obtained and applied 915to the request 903 for access. As part of this application, Internetaccess is restricted based on the content service definitions (e.g.,filters are applied based on URLs, application types, IP address,protocol, or other such considerations).

As a result of the rules application, the request for access 903 iseither allowed 917 or denied 919. In the case where the request foraccess 903 is denied 919 and it was a browser request, that request isredirected 921 to a designated website or portal, where the subscribercan choose content and application services or session offers, or managetheir account. If the request is not browser-based, then a requestdenied notification 923 is sent to the mobile device/subscriber 904. Itis to be noted that the rules have a hierarchy and can be applied to asubscriber, a group of subscribers, a company, a country, etc.

FIG. 17 depicts a particular, non-limiting embodiment of a systemarchitecture 951 which may be utilized for administration, activationand provisioning of content and application services within the contextof some of the restricted or metered bandwidth control paradigms of thetypes described herein. The system architecture 951 comprises a webportal 953 which accesses a service network 955 over a mobile network957 (with or without an active session) or over the Internet 959. Theservice network 955 controls access to the Internet 961.

As seen therein, a subscriber or plan administrator for group plans usesa laptop, notebook or other mobile communications device to access theweb portal 953 from which the subscriber or plan administrator creates aservice request 973 involving a selection of content or applicationservice. The web portal 953 may be accessed over the mobile network 957(with or without an active session) or over the Internet 959. Theservice administration 963 provides updates and deletes rules asnecessary and defines relevant groups/hierarchies 965. Notably, nochanges are required to applications on the laptop, notebook or othermobile communications device being used by the subscriber/administrator,since any defined rules or policies are applied in the service network955.

When a subscriber makes an Internet service request 973 via the MobileOperator Network 957 it is processed as a real-time Internet trafficrequest 967. A check is done to determine if there is an active sessionfor this subscriber. If there is an active session then session based971 processing is performed and the request is granted access 979 on theInternet 961.

If there is no active session (based on time and data) that allows thedevice to access the entire Internet 961, then the selection is passedto CAS processing 969, where a request for service provisioning oractivation 975 is made which specifies the service requested and thesubscriber or device ID. If the request is granted 979, then the contentor application service that was requested is permitted to be accessed onthe Internet 961. In either case, over time, new services are created983 with rules 965, and groups or hierarchies are defined.

As noted above, some of the systems and methodologies disclosed hereinfeature the concept of fractional applications, that is, mobile accesswhich is restricted to a particular application or set of applicationson a network (such as the Internet), as opposed to general access to thenetwork. In some of these systems and methodologies, these fractionalapplications may be assembled into product catalogs, and the productcatalogs may be combined with various service rules to provide a varietyof service offerings.

FIG. 18 depicts a particular, non-limiting embodiment of the foregoingtype of fractional application system 1001. As seen therein, this systemmay be utilized to provide end users 1007, 1015 on a first network 1018with fractional access to applications (such as, for example, web sitesor web-based products or services) on a second network 1021. In apreferred implementation, the first network 1018 may be, for example, aprivate network maintained by an MNO, and the second network 1021 maybe, for example, a public network such as the Internet. In the system1001 depicted, a first database 1011 is provided which maintains afractional application product catalog and the associated service rules.The first database 1011 may store information such as the product ID ofeach application in the product catalog and associated information suchas, for example, locational information (e.g., where the application isavailable), the duration over which the user is granted access toparticular applications in the product catalog, and the price termsgoverning access to these products. The associated service rules mayinclude such information as the service access/denial list (which mayinclude, for example, URLs, IP addresses and protocols for which accessto a given application is granted or denied), settlement rules, andservice descriptions.

The first database 1011 may be modified by way of an administratorversion 1005 of the product catalog and service rules, which is accessedby the system administrator 1003 through a suitable user interface (UI).The UI allows the system administrator 1003 to add new applications andservice rules to the administrator version 1005 of the product catalogand service rules, and to delete, update or otherwise modify existingapplications or service rules. Once these changes are committed, thefirst database 1011 is updated to reflect these changes.

A network appliance 1017 is provided in the first network 1018 whichserves as a gateway to the second network 1021, and hence controlsaccess to applications on the second network 1021 by the end users 1015on the first network 1018. Such access is governed by internal rulesmaintained in a second database 1019. As updates are made to the firstdatabase 1011, the fractional application service loader 1013 propagatesapplication and service rule information needed for access enforcementto the second database 1019.

The system 1001 is further equipped with a service handler 1009 whichhandles service activation, expiration and renewals. End users 1015 onthe first network 1018 may access the service handler 1009 via asuitable UI or web interface to request activation of a fractionalapplication or service, or renewal of an existing activated fractionalapplication or service. The device 1007 used by the end user 1015 toaccess the service handler 1009 may be the same as, or different from,the device for which service activation or renewal is being requested.Although depicted as a laptop PC, this device 1007 may be any suitabledevice including, but not limited to, tablet PCs, desktop PCs, mobilecommunications devices, or mobile technology platforms.

The service handler 1009 verifies the application/service requests and,if allowed, updates the network appliance with the subscriberinformation of the requesting end user 1015 and the application orservice allowed. Requests by the end users 1015 are either allowed ordenied by the network appliance 1017, based on the internal servicerules maintained in the second database 1019.

C3. Browser-Based Redirects

In some of the systems and methodologies disclosed herein, browser-basedredirects may be utilized as part of the white label process. Hence, onthe client side, a browser attempting to access a network may beredirected to a landing page utilizing a GSM or CDMA network. This isanalogous to the situation in which browsers are redirected to a landingpage on a Wi-Fi connection in a public establishment such as a hotel,where the user is then required to enter information in order to use theestablishment's Wi-Fi network. In the present case, a similar experienceis delivered over a GSM or CDMA modem instead of a Wi-Fi modem.

D1. Conclusion and Qualifiers

As used herein, the term “pipe” refers to a technique for passinginformation from one program process to another. Unlike other forms ofinterprocess communication (IPC), a pipe is one-way communication only.Basically, a pipe passes a parameter such as the output of one processto another process which accepts it as input. The system temporarilyholds the piped information until it is read by the receiving process.

While the systems and methodologies disclosed herein have beenfrequently described or exemplified with reference to mobilecommunications devices in general, and mobile phones in particular, oneskilled in the art will appreciate that these systems and methodologiesare not necessarily limited to being used in conjunction with suchdevices, but instead have application to, or may be leveraged by, a widevariety of communications devices. Such communications devices include,but are not limited to, personal digital assistants (PDAs), mobile orcellular phones, portable e-book readers, notebooks, netbooks, laptops,personal computers (PCs), navigational systems, televisions, displays,and other such devices.

One skilled in the art will further appreciate that the systems andmethodologies disclosed herein are not necessarily limited to anyparticular type of network or communications means or medium. Thus, forexample, the systems and methodologies may be implemented over theInternet, wide-area networks (WANs), local area networks (LANs),intranets, and various combinations of the foregoing. These networks maybe radio-based, hardwired, optical, and various combinations of theforegoing, and may operate over various frequencies of theelectromagnetic spectrum.

One skilled in the art will also appreciate that the systems andmethodologies disclosed herein are not necessarily limited to anyparticular type of business model, arrangement, or business. Thus, forexample, while the systems and methodologies have been frequentlydescribed herein in reference to MNVEs, MNVOs, MNOs, and the like due inpart to the current prevalence of these models, businesses andorganizations, it will be appreciated that the systems and methodologiesdescribed herein may have broader applications and are not necessarilylimited to these models, businesses and organizations.

One skilled in the art will also appreciate that the systems andmethodologies disclosed herein are not necessarily limited to anyparticular protocol. Thus, while reference has been made herein to SDP,SIP, MLP and other such protocols, it will be appreciated that suchprotocols are subject to change, and that the systems and methodologiesdescribed herein may utilize or implement new or different protocols.

The above description of the present invention is illustrative, and isnot intended to be limiting. It will thus be appreciated that variousadditions, substitutions and modifications may be made to the abovedescribed embodiments without departing from the scope of the presentinvention. Accordingly, the scope of the present invention should beconstrued in reference to the appended claims.

1. A method for controlling access to applications available on a secondnetwork by a plurality of client mobile communications devices on afirst network, wherein the first network includes (a) a first databasecomprising (i) a product catalog which contains a listing of a subset ofthe applications available on the second network, and (ii) a set ofservice rules which governs access to any of the applications in theproduct catalog by the client mobile communications devices, (b) asecond database which specifies the applications that have beenactivated for each of the plurality of client mobile communicationsdevices, and (c) a network appliance which is in communication with thesecond database and which restricts access by each of the client mobilecommunications devices to the respective applications specified asactive for that device, the method comprising: receiving a request, fromone of the plurality of client mobile communications devices, for anaction selected from the group consisting of (a) activating anapplication, and (b) reactivating a previously activated application;determining whether the request is allowable by (i) ascertaining whetherthe requested application is in the product catalog, and (ii)ascertaining whether the service rules permit the client device toaccess the requested application; if the request is allowable, updatingthe second database to indicate that the application has been activatedfor the requesting client device; and if the request is not allowable,sending a notice to the requesting client device that the request hasbeen denied.
 2. The method of claim 1, wherein the first network is aprivate network maintained by an MNO, and wherein the second network isa public network.
 3. The method of claim 2, wherein the second networkis the Internet.
 4. The method of claim 1, wherein the network applianceoperates as a gateway to the second network.
 5. The method of claim 1,further comprising: receiving a request, from one of the plurality ofclient mobile communications devices, for access to an application onthe second network; if the application is specified as activated for theclient mobile communications device, then allowing access to theapplication.
 6. The method of claim 5, further comprising: if theapplication is not specified as activated for the client mobilecommunications device, then denying access to the application.
 7. Themethod of claim 1, wherein reactivating a previously activatedapplication includes reactivating a previously activated applicationthat has subsequently lapsed.
 8. The method of claim 1, wherein therequest is for activating an application.
 9. The method of claim 1,wherein the second database includes a listing of applications from theproduct catalog, along with an indication of which of the applicationshave been activated for each of the plurality of client mobilecommunications devices, wherein the network appliance has associatedtherewith a service loader which is in communication with the firstdatabase, and wherein the service loader periodically updates thelisting in the second database to reflect changes in the productcatalog.
 10. The method of claim 9, wherein the service loader updatesthe listing in the second database by adding to the listing anyapplications that have been added to the product catalog.
 11. The methodof claim 9, wherein the service loader updates the listing in the seconddatabase by deleting from the listing any applications that have beendeleted from the product catalog.
 12. The method of claim 1, wherein theset of service rules in the first database include information selectedfrom the group consisting of (a) settlement rules, (b) access/deniallists, and (c) service descriptions.
 13. The method of claim 12, whereinthe set of service rules in the first database includes an access/deniallist, wherein the access/denial list includes information describingapplications or services to which access by the client mobilecommunications devices is granted or denied, and wherein the informationis selected from the group consisting of URLs, IP addresses, andprotocols.
 14. The method of claim 12, wherein the set of service rulesin the first database includes an access/denial list, and wherein theaccess/denial list includes location information which specifieslocations from which access to the applications or services by themobile communications devices will be permitted or denied.
 15. Themethod of claim 12, wherein the set of service rules in the firstdatabase includes an access/denial list, and wherein the access/deniallist includes duration information which specifies the duration overwhich access to the applications or services by the mobilecommunications devices will be permitted or denied.
 16. The method ofclaim 1, wherein the first network further comprises an administratorversion of the product catalog and service rules which is maintained bythe network administrator of the first network, wherein the networkadministrator makes periodic modifications to the administrator versionof the product catalog and service rules, and wherein, once thesechanges are committed, they are propagated to the first database. 17.The method of claim 1, wherein the first network further comprises aservice handler which handles service activation, service expiration andservice renewals for the plurality of client mobile communicationsdevices, wherein the service handler further comprises a user interface,and wherein the user interface may be utilized to request activation ofan application or service.
 18. The method of claim 17, wherein the userinterface may be utilized by the owner of a client mobile communicationsdevice to request activation of an application.
 19. The method of claim17, wherein the user interface may be utilized by an employee of an MNVEto request activation of an application or service.
 20. A tangiblemedium containing suitable programming instructions disposed in atangible, non-transient medium which, when executed by a computer, causethe method of claim 1 to be carried out.